Use the testing tool’s ingestion tuning as defaults - #6022

Error and audit instances currently need explicit configuration to use the ingestion profile pinned by the testing tool. Apply that profile when settings are omitted, while preserving explicit overrides.

Apply the same concurrency default to error-ingestion-only hosts. Keep monitoring instance defaults unchanged. Preserve explicitly configured batch sizes and timeouts, including a zero timeout.

Storage behavior

Keep the existing parallel-writer defaults and safety checks:

• RavenDB error ingestion uses one writer because concurrent batches can merge updates into the same failed-message document without ordering guarantees.
• SQL Server and PostgreSQL error ingestion use four writers.
• Audit ingestion uses four writers on all three providers. RavenDB audit batches write independent documents through separate bulk-insert operations.

No separate SQL tuning profile was found in the repository. These defaults match the testing tool; this change does not establish that they are optimal for every storage provider or deployment.

Operational impact

The 100 ms timeout can add up to 100 ms of batching latency at low message volumes. Higher receive concurrency can increase resource usage. In the error instance, the shared concurrency setting also controls the hosted endpoint, retry forwarding, and throughput collection receivers.

Update the ingestion design, configuration docstrings, and affected test expectations.